Release 10.1A: OpenEdge Development:
AppBuilder

Why use multiple layouts?

The following list identifies just a few of many different usages you might consider to employ multiple layouts:

If you plan to run an application in different run-time environments such as MS-Windows and a character-based terminal, you might want to adjust the application’s interface for each environment. If you are using SmartObjects, you might want to build a single master file for a SmartDataViewer or SmartContainer that provides a choice of visualizations. One solution is either to maintain a separate version of the application for each environment or to create a separate SmartObject instance for each visualization. This approach requires that you maintain and deploy multiple sets of source code.
Another solution is to use the AppBuilder’s capability to support multiple layouts in a single procedure file. The advantage of this approach is that you maintain and deploy one set of source files for an application. When you run a procedure file that contains multiple layouts, the procedure file adjusts its interface to suit the current run-time environment. You can also switch between layouts at run time.
Multiple layouts can help you internationalize an application. For example, you might have an application that helps you to distribute products globally. Since different countries have different address formats and information requirements, your application can employ multiple layouts to effectively address this addressing issue.

For more information on multiple layouts and international considerations, see OpenEdge Development: Internationalizing Applications .